Repository navigation
Release 0.26.0: Listen (narrated journeys) and sub-line marks - #7
Merged
Merged
Conversation
…k follows the voice
A journey with `<journey>.podcast.json` next to it (and its audio) gets a ▶ on its row and a player at the bottom of
the journey panel: play/pause, ±15 s, previous/next step, speed, and a timeline marked by step (hover names the step,
click or drag to seek). The walk follows the audio: at any time it is where the podcast is at that time (the step
opened as a reader's move would, the animation on that beat). A seek applies that view directly, backwards too, and of
quick seeks only the last one. Next, Previous, a step or a beat the reader picks moves the audio to its first part; a
step the podcast skips, or ending the walk, pauses it. The audio plays in the panel's webview (kept while hidden), so
it goes on behind another tab. Ctrl+' Space / ← / → from anywhere; a status bar item.
- src/podcast/model.ts: the format, checked against the journey (a missing beat shows the step only; an unknown step
keeps the view before), view at a time, chapters, journey → audio times, LatestWins (seek coalescing). Unit tests.
- src/podcast/player.ts: discovery next to the journey, audio → walk and walk → audio, commands, status item.
- media/journey-podcast.js/.css: the bar, outside #app so re-renders never touch the audio or a drag.
- The panel: audio from the journeys folders (localResourceRoots, CSP media-src); beats preset before the step opens
(no first-beat flash); the scene can show a beat without its flight (a jump).
- VS Code's webviews play audio only after a click or key in them: the first Play focuses ▶ ("Press Space to play").
- test:podcast harness (three widths, seeks forwards/backwards, drag, hover, keys, step click, missing beat) and an
integration suite in real VS Code (mp3 plays; seeks; quick seeks; Next/Previous; hidden panel; a 10-minute file
seeked 9 minutes in). The main integration run opens a DevTools port for the real click.
- docs/podcast-format.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…/ Recap on the map); real-window shots of the player Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every problem with its level (error: it can't be played; warning: it plays, but a part is not what the file says) and where it is (a JSON path, the segment). Covers the shape (invalid JSON with its line and column, version, missing / empty / non-list segments), the audio (a path out of the journeys folder is refused, missing or empty file), the timing (overlaps, out of order, end before start, past the duration, past the real audio, a cut-off audio), the links (unknown step, beat out of range, bad at) and the journey it was written for. Unknown fields (e.g. say) are accepted. The cases live in test/fixtures/podcast/cases.json so another implementation can run them too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ed from The panel loads the audio whole (fetch, then a blob: URL) before it plays: a server that ignores HTTP Range (VS Code for the web, remote windows) serves media Chromium can't seek in, and a seek there fell back to 0:00 while the walk had already moved. When the fetch fails, the file's own URL plays and a seek reports where the audio ended up once it is done, never the time asked; a seek that lands elsewhere is said in the bar and logged. Also: the status bar is told each second the bar shows (one clock); a play() that fails, a media error or a clock that stops while playing leaves it paused with the reason; Space and K play and pause anywhere in the panel but where you type, also after a beat's ‹ › was clicked; a pause can carry a note and where the next ▶ starts. The panel test serves the audio without Range, and checks a failed fetch and an audio that can't play. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…lk's tabs close on their own goToStep takes the beat of the animation it opens on: when that beat's code is in another file, that file is the one opened (by the beat), never the step's own file first. closeWalkTabs closes the walk's preview tab (a step's file, or a file its animations show), as Finish did. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s and reports from before a seek no longer move the walk back - Each report of the panel keeps where that journey's podcast is (in memory, and in the workspace state on a pause, a seek, leaving): another journey, the walk ending or the panel closing never lose it, and ▶ (the row, the command, the player) goes on there, or at the step the walk is on. - Next, Previous or the storyline onto a step the podcast skips: the walk stays there, the audio pauses and says so; ▶ goes on with the next part after that step. Reports from before a pause, like those from before a seek, are ignored. - The podcast file rewritten: the same moment of the same part (by segment id when its times moved), playing on if it was. - A seek onto a beat in another file opens that file directly; the intro (the map, no step) closes the walk's code tab. - The panel tells which journey a report is about, so a report of the audio leaving is never taken for the one arriving. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, rewritten file, kept place, beat in another file ONLY_PODCAST=1 (with ONLY_MAIN=1) runs main/podcast.ts alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A podcast file that can't be played no longer vanishes: its row keeps a
greyed play button and the tooltip says why, the panel shows one line,
"Podcast unavailable", with Show why (the Problems view), and Play says why.
Every problem is a diagnostic on the .podcast.json (on the field or segment
at fault) and a warning line in the output, once per change. One that plays
says what is wrong in one short line in the panel and the row's tooltip
("2 parts can't be shown", "Written for ...", a cut-off audio in plain
words, measured once the panel has loaded the audio).
A file that breaks while it plays (half-written) keeps the last good version
playing and says so; the status item goes when its podcast goes, so a click
on it always does something. The audio file is watched too: putting it back
brings the podcast back. An interrupted play (AbortError) is no longer a
warning; a media error names the file and what it most likely is.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ngs in the player ONLY_PODCAST=1 runs the podcast's tests alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ten files, keys Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The extension's podcast validator, rule for rule, in the code-journey skill's script: PROBLEM when the extension won't play the file, WARNING when a part is not what the file says. The audio's length comes from the argument, a WAV header or ffprobe. check runs it when the podcast exists. The shared cases run through both implementations. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ips; the skill knows podcasts docs/podcast-format.md: the validation rules (errors, warnings), what the row, the panel, the Problems view and the output show, the last good version, the watched audio, the optional say field. The code-journey skill gets a Podcasts section (journey.py podcast); its podcast command counts as checking in the progress line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ree widths Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… it isn't playing on its own Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…k and resume fixes scan() and the panel's episode do both: the validator's playable / unavailable / last-good logic and notices, plus the per-journey episode key, the kept place, the time remapped when the file is rewritten, and play-on once a podcast that went while playing is back. In the panel, the whole-file (blob) audio is unloaded and revoked when a podcast becomes unavailable; a notice on the same audio keeps it playing. podcastError and podcastMeta carry the journey they are about (`of`); AbortError goes to the log at debug level; an audio that can't be decoded is named with its file and size. The status item is rendered again once a move of the walk is done (it could keep the step it showed while the walk was elsewhere). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hen present
A segment may carry sentences: [{ start, text }], when each sentence of its
text starts in the audio. resolveEpisode keeps them only when all are usable
(a non-empty list, starts in order, each within the segment); otherwise the
player estimates the times from the text, and the check says why with one
"sentences" warning on the segment. Same rule in journey.py podcast; four
shared cases run through both.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, reused ids with times, narration order, recorded for an older commit; stray podcast files say why they are ignored Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the reader's draft; the journey you're in is focused, never closed; an open panel is never closed by the layout rule; Ctrl+' V gives a narrow panel room for the map; beats reveal from column 1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hile playing; a shorter part in another file stays in the view before); ⏮ is always the part before, as the step card's Previous; segments keep their step's id Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… with one transport, the map's moments close the walk's code, a note or a question pauses it, the step kept by id, quick skips debounced, unnarrated beats pause, the end of the walk ends the session, pauses and stops logged Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every Playwright launch passes --mute-audio; the integration run drops PULSE_SERVER and starts VS Code with --mute-audio. Muted media still plays and its time still moves, so the audio tests keep their meaning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…status item are its remotes The audio moves out of the journey panel into a webview view, Listen (Code Notes side bar, under Journeys, retained while hidden): closing the panel, or a layout that hides it, no longer stops the episode. The panel's player draws the state the view reports (podcastState, relayed) and asks the view through the extension (podcastAsk); a reopened panel shows where the audio is. The status item says Listening / Paused / Ended (the glyph is the state), its tooltip holds the actions with their keys, its click opens the map. The player: the caption is the sentence being said (the file's sentence times, else estimated), two lines at most, in parts, never cut, the speaker on a voice change; the timeline is the full width with a mark per step (at least 8 px), the playhead always shown, hover gives the time and the step in full and goes on leave, a cut-off audio's unreachable part greyed; ⏮ ▶ ⏭ first in a narrow panel, the ±15 s buttons gone (keys stay); a speed menu 0.75-2x, mute (M), both remembered; K and M by key position; ARIA slider keys, value text with the total, one polite announcement per step; Media Session; a real end (Replay, Walk it yourself, Next journey); a seek after the end plays. The panel: the storyline is the chapter list (start times, the row being said, not narrated, a per-step play that stops at the step's end, a transcript per row findable when shut); while playing the header is one line and the beat's sentence and code snippet give way to the caption; a step change by the voice scrolls to it. The scene's beat shows as dots. Commands: Listen to Journey, Listen: Play/Pause, Back 15 s, Forward 15 s, Previous Step, Next Step (Ctrl+' Shift+Left/Right); ids unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…dcast A row says its podcast (♪ 12:47; ♪ Listening; ♪ Paused at 3:38) with a tooltip line and its accessible name, and offers ▶ Listen, ⏸ while it plays, or Resume. The journey being walked is listed once (Continue, not again under In this file). Open Journey... shows the length and a ▶ button; the panel's journey list marks podcasts and the one playing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…sserts layout shoot.mjs loads both pages with the extension's part between them. A layout matrix (190, 340, 700, 1200 px; light and dark; paused, playing, ended, notice, unavailable) measures every control (inside, not cut, no overlap), the step marks' size, control priority, the two-line caption, the storyline's room, then clicks every control. The behaviour runs cover seeks, drag, hover, keys, the speed menu, mute, captions, the chapter list, per-step play, the transcript, the panel closed and reopened, the end, a streamed audio, an unplayable one and a cut-off one. The integration tests drive the Listen view, and closing the panel now keeps the audio playing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tons on that line Under 320 px the current row's ▶ and ≡ squeezed its title to a column of words (the layout check caught it at 190 and 700 px). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… pointer Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iped; its test uses an episode longer than its audio A truncated mp3 whose header keeps its full length reads as full length in the player, so the harness tells the two lengths apart through the episode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… follow lock, the view hold, the map's moments, one code group never on a draft, widths kept on focus (VS Code expanding a panel at its minimum is undone), Ctrl+' V, a note or a question pausing, the step kept by id, a removed step, quick skips, an unnarrated beat, End Journey, a journey without a podcast, nothing piling up End Journey during a pending seek, and a playing report from before it, no longer start the walk again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…line card, one transport, the map's moments, notes and questions pause it, the panel keeps its width), the journey edited under it, the new checks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the panel as it is revealed; a layout the extension just set is the one kept Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…en view The walk side (follow lock, one-line card with one transport, view hold, map moments, panel width kept, notes and questions pause, step kept by id, more podcast checks) merged onto the Listen view, where the audio now lives: - every command to the audio goes to the Listen view; End Journey and another journey still end the listening session through it - the step card's transport works whenever the Listen view has the episode, also with the panel closed - closing the panel keeps it playing (only the status item and the card are redrawn) - a panel newly showing a journey whose place was kept makes it the paused session again; a podcast file read again doesn't - ⏮ is always the part before in the Listen player as well - tests: the walk tests start a new Listen view with a click in it; the nothing-piles-up check starts from no code tabs (the note test pins the reader's tab) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A segment's optional `marks` light parts of the code while the voice says a phrase: whole lines, or a `match` (its `nth`) within them, down to the characters. - model.ts: marks parsed (bad ones left out), when each lights (0.12 s before its word, the same phrase twice together), which are lit at a time and which is the focus, the view hold for marks in another file, the match found within its lines or re-found within 20 lines, else the whole lines - marks.ts: two decoration types in theme colours (the newest: a box in the cursor's colour; earlier ones in the segment: fainter); cleared at the next segment - player.ts: at every report exactly the marks lit by then in the segment playing then (a seek, paused too); the next one lit on time by a timer; an off-screen mark is scrolled to, never under the follow lock; a mark in another file opens it only after the view hold, else it is skipped (debug log) - validate.ts and journey.py (lockstep, shared cases): mark shape, time within the segment and in order, phrase in the text, a map segment's marks need a file; against the repository: the file, the lines, the match (and whether it is found nearby) - docs: Marks in the podcast format (fields, player rules, checks); CHANGELOG Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…y.py reads mark files with a relative repository path; the follow-lock test scrolls the reader clearly away from the mark Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ck with a bar on the left (no lines between rows), a mark within a line tints its characters; earlier marks a lighter tint Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When the next mark, beat or step is out of view while it plays, the code no longer
jumps at once: a cue at the editor's edge says where it goes ("↓ 340", "↑ 212",
"→ main.ts") 0.8 s before; the move waits until what was lit last has been on screen
codeNotes.listen.readBeforeMove seconds (2.5), then the audio waits
codeNotes.listen.settleAfterMove seconds (0.8) with the new mark lit. The player's
quiet line says it is waiting; ▶ or Space plays on at once. No waits when the code is
on screen, under the follow lock, in the 1.5 s of audio after the reader's own seek,
or on the map. End Journey during a wait drops the move.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… voice A camera wait is now a hold, not a pause: the audio stops, but the player (both), the status item, the Journeys row and the step card keep showing it playing; the edge cue is the only sign (the "Waiting to move" line under the player is gone). Space or ⏸ during a wait is the reader's pause and drops the move. The hold is checked against the audio's own reports: when its time still moves 0.25 s after asking, the wait is dropped, logged once, and the walk goes to what the audio says now (its view and marks at that time, no late moves); waits then stay off for 30 s (until a seek or a new session). Playing on, or scrolling the code, during a wait ends it the same way. Moves that waited are never replayed. Keeping time: the Listen view's reports carry when they were said; the panel's player counts from then, not from when the relay brought them, and the extension re-bases each report by how late it came (beyond the quickest one) and applies only the newest of a run of plain reports. Captions of a long sentence change part when its words are said: the marks' phrases anchor the clock. Follow lock: the reader's scroll is measured from where the extension last left the code, so a slow scroll in small steps counts; the step card growing or shrinking (pause, play) no longer counts as the reader. Marks brought on screen keep column 1 in view; the code scrolls right only for a mark starting past the right edge. Tests: continuous play through out-of-view moves with the Listen view collapsed and the panel closed (the audio stands still in each wait, nothing says paused, the marks are the audio's after each move); a hold the audio ignores (dropped, the walk resyncs within ~300 ms); a wait is no pause, and small-step scrolls open the follow lock while card resizes don't; column 1 kept on reveal; ten minutes at 2x with waits (extension time, captions and marks match the audio). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
VS Code's window plays a webview's audio only after a click or a key in that same webview (autoplayPolicy user-gesture-required; the iframes' allow=autoplay does not change that). A click in the workbench (a Journeys row, a command) or in another webview never counted, so every first start stopped at a second ▶ in the Listen view. Each player now unlocks its <audio> on the first real click or key in its page and says so; the extension plays the episode where that happened. A ▶ in the journey panel plays in the panel (the Listen view becomes its remote, and takes the audio over when the panel closes or shows another journey). A start before any click in either player opens the panel paused with its ▶ focused: Space or one click there plays it; no hint text, no focus jump to the side bar. The integration test starts from a command, a real Space in the panel, a real click on a new panel's ▶ and a command again, asserting the audio's own clock moves each time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The step card is its header line only ("3/14 · title"; Follow along under it
while the reader looks around), above the signature of the function the step
is in. Paused, the full card comes back above the step's first line.
- No value hints or code-link lines while it plays; back on pause.
- The newest mark is the one colour on the code: its own theme colour
(codeNotes.markBackground), a fill only, no bar, no scrollbar ticks. Earlier
marks keep their lighter tint.
- While it plays the step's lines have a thin grey bar (no tint, no ruler
tick), the beat's box is not drawn and the caret is not moved to it, and the
narrated code shows no note bars, washes or ruler marks.
- Test: listenEditor.ts (card placement and what goes quiet, with pictures
under CODE_NOTES_SHOTS); podcast.ts expects the header-only card.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One player: while the journey panel shows the episode, the Listen view is one line (the journey, play/pause, the
time); the whole player shows there only when the panel is closed. While it plays the panel is a one-line header
("Step 6 of 14 · title", "Intro", "Recap") and the step's animation alone in the same box every step (the map for a
step without one; names only, zoom on hover, at the intro and the recap). On pause the chapter list comes back
(number and title, the step being said bold, ▶ on hover, one Transcript switch showing the current step's), with ‹
and End; the header stays one line until the episode ends, and no "New here?" bar meanwhile.
The player: a plain ⏸ like ⏮ ⏭, ticks instead of step numbers under the timeline (hover "Step 6 · title · 5:23"),
no step name beside the clock, a borderless "1×" that cycles 1 → 1.25 → 1.5 → 2, no mute button (M stays), one key
per tooltip, neutral greys. The end is Replay · Walk it yourself · Next journey only. A remote's play/pause is no
longer undone by a report sent before it.
Beside the code the panel is 360–420 px while an episode is on (listeningShare); intro and recap keep the map.
Sentences no longer split at a dot inside an identifier; the animation hides a wire whose other end is out of view,
and a packet stops before its receiver instead of over it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…laying Below the map's minimum width (240 px) the playing box had nothing to show, so the panel was a header over nothing; there the chapter list stays. The harness checks that at 190 px, and waits for the intro's header instead of reading it once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The podcast's mark type, its checks (lines, file, match, nth), findMark and the code check move to src/marks/model.ts; how marks are drawn (focus and dim, within a line or whole lines) to src/marks/lights.ts. The podcast keeps its timing (phrase, at) on top. No behaviour change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A step or beat may carry marks (lines, match, nth, file), as a podcast segment does without the time. Opening the step lights its marks; a beat lights its own as the focus, the earlier ones dimmer. While there are marks the step's lines get the thin grey bar and the beat's line no box. Marks in the step's file move with the step, a match is re-found within 20 lines, one not found lights nothing (logged once). A step without marks looks as before. Documented in docs/journey-format.md, "Marks". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
journey.py mark / marks / rmmark; check validates step and beat marks (match on its lines, nth, file), warns on too many, unnamed or whole-line marks, and fix moves a match found a few lines off. The shape and code checks are shared with the podcast's and give the extension's messages word for word (test/cli/journeyMarks.test.mjs). SKILL.md: mark the call, argument, condition or field a step names. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The Listen view is there only while a journey is listened to (playing or
paused; codeNotes.listening), with no empty-state text; it goes a moment
after the last session ends, so going from one journey to the next keeps
the view and its unlocked audio. A podcast that can't play never shows it.
- Journeys row: "♪ 12:47" only (no Listening, Paused at, step or speaker
icon); ▶ unless it plays (paused, ▶ goes on); no ⏸ / Resume / greyed ▶
row actions; the tooltip has a podcast line only for one that can't play.
- Open Journey…: "Title ♪", the question as the description; the journey
listened to says "listening", without ▶ or the walk's icon.
- Status bar: one item, only while the journey panel is off screen
("Listening · 6:58", a one-line tooltip), gone after the end; the walk's
"3/14" steps aside meanwhile. No status-bar flashes (resume, follow lock,
note being written, removed step): the output logs them.
- Palette: the transport commands only while a journey is listened to;
"Listen: Pause/Play", "Listen: Open the Map".
- Notice: "N problems", N as the Problems view counts; a bad beat is said by
its step ("Step 1: no beat 99 (it has 5); showing the whole step") and its
marks are not reported again; "Code changed since recording: steps 2, 5".
journey.py says the same.
- A journey panel closed while VS Code restores it no longer throws "Webview
is disposed" out of the serializer (and the activation): the panel is
drawn before it is taken as the map, and the restore checks it is still
open. The map no longer reads a closed panel's visibility while closing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.26.0: Listen (narrated journeys) and sub-line marks.
<journey>.podcast.json+ audio, see docs/podcast-format.md) can be listened to. The walk follows the voice: steps open, animations move beat by beat, and marks light the exact call, argument or condition as it is said. The player sits in the journey panel; the audio keeps playing when the panel closes. Camera moves give time to read; a calm, decluttered layout while listening.marksin docs/journey-format.md); the code-journey skill writes and checks them (journey.py mark / marks / rmmark).See CHANGELOG.md for the full list.
🤖 Generated with Claude Code